The Custom Object Extension framework of adTempus allows you to create custom objects such as Tasks, Triggers, Conditions, and Response Actions. This offers tighter integration with adTempus than does implementing custom logic in Scripts, and allows your Custom Objects to have user-configurable settings. Custom Object Extensions are written using Microsoft .NET programming languages.

Settings for your Custom Object are serialized and saved with other job settings in the adTempus database.

Custom Object Architecture

When you create a Custom Object, you implement the following classes:

• A settings class (implementing ICustomObjectSettings) stores the user-configurable settings for your task.
• A factory class (implementing ICustomObjectFactory) is responsible for creating new instances of your settings class and for deserializing settings that were previously serialized and stored in the adTempus database.
• An executor class (implementing an interface derived from IExtensionExecutor) executes the operation.
• Optionally, you may provide a custom user interface for editing your settings. If you do not provide a custom user interface, settings can be edited in a Property Grid.

Custom Object Definition

Custom objects are defined to adTempus using an XML file with the extension ".adTempusExtension". Refer to the adTempusExtensions400.xsd schema file and sample definition files contained included in the extension examples download for details.